---
title: Introduction
description: Re-usable components built using shadcn/ui, Radix UI and Tailwind CSS.
---

This is **NOT** a component library. It's a collection of re-usable components that you can copy and paste into your apps.

**What do you mean by not a component library?**

We mean you do not install it as a dependency. It is not available or distributed via npm.

Pick the components you need. Copy and paste the code into your project and customize to your needs. The code is yours.

_Use this as a reference to build your own component libraries._

## FAQ

<Accordion type="multiple">

<AccordionItem value="faq-0">
<AccordionTrigger>

Is it a replacement to shadcn/ui?

</AccordionTrigger>
<AccordionContent>

No, it's not a replacement to <Link href="https://ui.shadcn.com/">shadcn/ui</Link>.
Instead, Plate UI an extended collection of components built on top of <Link href="https://ui.shadcn.com/">shadcn/ui</Link> and <Link href="https://www.radix-ui.com/">Radix UI</Link>, specifically designed for **rich-text editor** design. For other parts of your app, you should continue to use other components such as <Link href="https://ui.shadcn.com/">shadcn/ui</Link>.

Plate UI adheres to the same conventions, usage, and patterns as <Link href="https://ui.shadcn.com/">shadcn/ui</Link>, meaning you can seamlessly integrate it with your existing <Link href="https://ui.shadcn.com/">shadcn/ui</Link> components rather than replacing them.

Next to <Link href="https://ui.shadcn.com/">shadcn/ui</Link>, Plate UI is the first published component registry.

</AccordionContent>

</AccordionItem>

<AccordionItem value="faq-1">
<AccordionTrigger>
Why copy/paste and not packaged as a dependency?
</AccordionTrigger>
<AccordionContent>
The idea behind this is to give you ownership and control over the code, allowing you to decide how the components are built and styled.

Start with some sensible defaults, then customize the components to your needs.

One of the drawback of packaging the components in an npm package is that the style is coupled with the implementation. _The design of your components should be separate from their implementation._

</AccordionContent>

</AccordionItem>

<AccordionItem value="faq-2">
<AccordionTrigger>
    Do you plan to publish it as an npm package?
  </AccordionTrigger>
  <AccordionContent>
    No. We have no plans to publish it as an npm package.
  </AccordionContent>
</AccordionItem>
<AccordionItem value="faq-3">
<AccordionTrigger>
Which frameworks are supported?
</AccordionTrigger>
<AccordionContent>

[Plate](/docs) and any framework that supports React. [Next.js](/docs/components/installation/next), [Remix](/docs/components/remix) etc.

</AccordionContent>
</AccordionItem>

<AccordionItem value="faq-4">
	<AccordionTrigger>
	Can I use this in my project?
	</AccordionTrigger>
	<AccordionContent>
Yes. Free to use for personal and commercial projects. No attribution required, but sharing your editor app <Link href="https://github.com/udecode/plate/issues/818">here</Link> is appreciated!

    </AccordionContent>

</AccordionItem>

</Accordion>

## Credits

- <Link href="https://ui.shadcn.com/">shadcn/ui</Link> - For the UI, the docs and the CLI.
- <Link href="https://radix-ui.com">Radix UI</Link> - For the primitives.
- <Link href="https://vercel.com">Vercel</Link> - For hosting.
- <Link href="https://shud.in">Shu Ding</Link> - The typography style is adapted from his work on Nextra.
- <Link href="https://cmdk.paco.me">cmdk</Link> - For the `<Command />` component.
